UCF STIG Viewer Logo

The EMM system supporting the Google Android 13 BYOAD must be configured to detect if known malicious applications, blocked, or prohibited applications are installed on the Google Android 13 BYOAD (DOD-managed segment only).


Overview

Finding ID Version Rule ID IA Controls Severity
V-258464 GOOG-13-800500 SV-258464r929208_rule Medium
Description
DOD policy requires BYOAD devices with DOD data be managed by a DOD MDM server, MAM server, or VMI system. This ensures the device can be monitored for compliance with the approved security baseline and the work profile can be removed when the device is out of compliance, which protects DOD data from unauthorized exposure. Detection via collecting and analysis of BYOAD generated logs for noncompliance indicators is acceptable. This detection capability must be implemented prior to AMD (Approved Mobile Device, called BYOAD device in the STIG) enrollment, AMD access to DOD information and IT resources, and continuously monitored on the DOD-managed segment of the AMD enrolled in the program. If non-DOD information (i.e., personal user data, device information) outside the DOD-managed segment of the AMD is required to be accessed, collected, monitored, tracked (i.e., location), or maintained, the circumstances under which this may be done must be outlined in the user agreement. Reference: DOD policy "Use of Non-Government Mobile Devices" (3.a.(3)iii). SFR ID: FMT_SMF_EXT.1.1 #47
STIG Date
Google Android 13 MDFPP 3.3 BYOAD Security Technical Implementation Guide 2023-09-19

Details

Check Text ( C-62204r929206_chk )
Verify an app vetting process is being used to vet apps before work profile apps are placed in the MDM app repository.

If an app vetting process is not being used to vet apps before work profile apps are placed in the MDM app repository, this is a finding.
Fix Text (F-62113r929207_fix)
Implement an app vetting process before work profile apps are placed in the MDM app repository.